![]() | ![]() | ![]() | ![]() | ![]() |
It is possible to create two SAS Warranty Analysis emerging issues analyses (Ad Hoc – Analytic and Ad Hoc – Threshold) using the same version of a data selection but for different days. If the configured numbers of days to wait before deletion falls between these two analyses, the filtered data might be deleted, even though the results for the later analysis are not deleted.
This should not affect SAS Warranty Analysis operations unless you try to drill into the emerging issues analysis. This analysis would have results but no filtered data. The system attempts to recreate the filtered data from the data mart, taking into consideration the warehouse refresh date of the original filtered data.
You can minimize the possibility of this incongruity occurring. Set the “Number of Days Before Inactive Subset is deleted” configuration parameter to a multiple of the extract, transform, and load (ETL) cycle. For example, if the ETL is performed weekly, set the parameter to 14,21,28,35.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Warranty Analysis | Microsoft Windows Server 2003 Datacenter Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Standard Edition | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
64-bit Enabled AIX | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
64-bit Enabled Solaris | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
HP-UX IPF | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Linux for x64 | 4.3 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |